◀ Prev • Parts • Full • Next ▶

It is also possible to run multiple instaces of RNS on the same system by specifying a different configuration directory for each instance of rnsd with --config=<config directory>, or --rnsconfig=<config directory> for any of the utilities. Running multiple instances uses more memory.

RNS includes a number of useful command-line utilities besides the rnsd daemon:

• rncp – File transfer utility

• rngit – Git repository node management

• rnid – Identity and encryption utility

• rnir – Distributed identity resolver (WIP)

• rnodeconf – RNode configuration and firmware utility

• rnpath – Path management utility

• rnpkg – Package manager (WIP)

• rnprobe – Probe utility

• rnsh – Remote shell utility

• rnstatus – Reticulum Network Stack status

• rnx – Remote execution utility

Subscribe to PyPi's RSS feed to be notified of new releases:

Use rngit to fetch the version number of the latest release:

Once RNS is installed, you can use rngit to update RNS over Reticulum.

Reticulum apps may be isolated by running a primary rnsd instance as a non-privileged user, and running each isolated app as its own user with its own rnsd instance/configuration, connected to the primary instance over a BackboneInterface.

The primary instance has a system-local BackboneInterface serving the apps' instances, and external interfaces for connecting to the wider network. Each isolated app points to the RNS configuration of its own instance (eg. rngit --rnsconfig=<app's rns config>), which in turn connects to the primary instance over a BackboneInterface.

Running multiple instances like this uses more memory and adds an extra hop, but the performance penalty is negligible.

◀ Prev • Parts • Full • Next ▶